Method and system for managing real-time bandwidth request in a wireless network

ABSTRACT

A method and system for managing real-time bandwidth request in a wireless network includes receiving a request for a connection for bandwidth of a cell of a wireless network. A subscription level associated with a connection is determined. The request for the connection is processed based on the subscription level.

TECHNICAL FIELD OF THE INVENTION

The present invention relates generally to the field of wireless communications, and more particularly to a method and system for managing real-time bandwidth request in a wireless network.

BACKGROUND OF THE INVENTION

Traditional wireless networks include a number of base stations (BTS) and one or more mobile switching centers (MSC)/base station controllers (BSC). The BTSs each cover a geographic region, or cell of the wireless network and communicate with mobile telephones in the cell. The MSCs/BSCs provide switch and soft handoff functionality for the wireless network. To support data calls, wireless networks typically include a data interworking function (IWF). The IWF connects the wireless network to the Internet or other data network.

Each cell of a wireless network is able to support a certain number or bandwidth of wireless calls. This capacity is a function of the maximum transmit power, frequency reuse, carrier to interference ratio, bit energy-to-noise ratio, effective bit-rate protocol and other criteria of the wireless link. To prevent the maximum power from being exceeded for a cell and thus damaging the transmitter, call and handoff admissions are blocked when the transmit power level exceeds established thresholds. Typically, the call blocking threshold is lower than the handoff blocking threshold to provide priority to existing calls entering the cell.

In operation, admission requests are processed as they are received. New call originations are blocked when the transmit power at the cell exceeds the call blocking threshold while handoff requests are still serviced normally. When the transmit power exceeds the higher handoff blocking threshold, both call origination and handoff requests are denied service.

SUMMARY OF THE INVENTION

The present invention provides a method and system for managing real-time bandwidth request in a wireless network that substantially eliminate or reduce problems and disadvantages associated with previous systems and methods. In particular, call origination, handoff, additional bandwidth and/or other suitable requests for bandwidth are differentiated based on user subscription levels to deliver differentiated tiered services to mobile users.

In accordance with one embodiment of the present invention, a method and system for managing bandwidth request in a wireless network includes receiving a request for a connection for bandwidth of a cell of a wireless network. A subscription level or other priority associated with the connection is determined. The request for the connection is processed based on the subscription level.

More specifically, in accordance with a particular embodiment of the present invention, the subscription level comprises a quality of service (QoS). In this embodiment, the request may be processed in order of its QoS-based priority.

Technical advantages of the present invention include providing an improved method and system for managing real-time bandwidth request in a wireless network. In a particular embodiment, the present invention provides QoS-based bandwidth allocation. Accordingly, bandwidth allocation priority is provided to users with higher priority subscriptions and wireless service providers are able to provide service packages based on differentiated wireless services.

Another technical advantage of one or more embodiments of the present invention includes providing QoS based queues for processing call origination, handoff and/or additional bandwidth requests in a wireless network. In particular, admission requests are queued based on their QoS priority with request in the higher priority queues given priority. Accordingly, use of bandwidth is maximized and limited bandwidth or power available during times of congestion is allocated to users subscribing to higher quality services.

Still another technical advantage of one or more embodiments of the present invention includes providing QoS based thresholds for processing call origination, handoff and/or additional bandwidth requests in a wireless network. In particular, requests are processed in the order received but using priority based thresholds. Accordingly, priority is provided to users with higher priority subscriptions. In this way, maximum usability and mobility is provided to users subscribing to and paying for higher quality of service.

Yet another technical advantage of one or more embodiments of the present invention includes tying the radio bandwidth allocation mechanisms in a wireless network to the Internet protocol (IP) quality mechanisms. In particular, the IP QoS mechanism is tied to the radio QoS mechanism such that users with higher subscription levels will observe lower bandwidth denial compared to users with lower subscription levels. As a result, wireless service providers can deliver differentiated tiered services to mobile users based on their QoS subscription.

Other technical advantages of the present invention will be readily apparent to one skilled in the art from the following figures, description and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like numerals represent like parts, in which:

FIG. 1 is block diagram illustrating a communications network in accordance with one embodiment of the present invention;

FIG. 2 is a block diagram illustrating details of a bandwidth allocation controller for the wireless network of FIG. 1 in accordance with one embodiment of the present invention;

FIG. 3 is a flow diagram illustrating a method for queuing bandwidth request for allocation in accordance with one embodiment of the present invention; and

FIG. 4 is a block diagram illustrating a method for bandwidth allocation control in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a communications system 10 in accordance with one embodiment of the present invention. In this embodiment, the communications system 10 includes a cellular wireless network in which terrestrial wireless transmissions originate in geographically delimited cells. It will be understood that the present invention may be used in connection with other suitable wireless networks.

Referring to FIG. 1, the communications system 10 includes a wireless network 12 connected to a wireline network 14 through a data gateway, such as a packet data serving node (PDSN) 16. The PDSN 16 comprises a router that directs traffic between the wireless and wireline networks 12 and 14. In one embodiment, the PDSN 16 includes a data interworking function (IWF) 18 that provides connectivity between the wireless and wireline networks 12 and 14 via circuit switched and packet switched wireless data protocols. It will be understood that connectivity between the wireline and wireless networks 12 and 14 may be otherwise suitably provided without departing from the scope of the present invention.

The wireless network 12 includes a number of base stations (BTSs) 30 connected to base station controllers (BSCs) 32. The BTSs 30 each cover a geographic region, or cell 34 of the wireless network 12 and communicate with mobile devices 36 in the cell 34. The mobile devices 36 may be cell phones, data phones, portable data devices, portable computers, handheld devices, handsets, portable network appliances or other suitable devices capable of communicating information over a wireless link 38.

The BSCs 32 are connected to each other, to the PDSN 16 and to a mobile switching center (MSC) 40. The BSCs 32 and the MSC 40 provide switch and soft handoff functionality for the wireless network 12. In this way, voice, video, data and other information is routed to and from the mobile devices 36 and connections are maintained with the mobile devices 36 as they move throughout the wireless network 12.

Wireless link 38 is a radio frequency (RF) link. The wireless link 38 may be based on established technologies or standards such as IS-54 (TDMA), IS-95 (CDMA), GSM and AMPS, 802.11 based WLAN, or more recent technology such as CDMA 2000 and W-CDMA or proprietary radio interfaces. In a particular embodiment, wireless link 38 comprises a code division multiple access (CDMA) link based on a CDMA standard and in which packets are segmented into radio frames for transmission over the wireless interface and reassembled by the receiving device to reconstitute the packets.

The wireline network 14 includes a packet network 50 connecting a number of servers 52 to each other and to the PDSN 16. The packet network 50 also connects the PDSN 16, and thus the wireless network 12 to the public switched telephone network (PSTN) 54 through gateway 56. Accordingly, mobile devices 36 may communicate through wireless network 12, packet network 50 and PSTN 54 with standard telephones, clients and computers using modems or digital subscriber line (DSL) connections or other telephony devices 58.

The data network 50 may be the Internet, intranet, extranet, or other suitable local or wide area network capable of communicating information between remote endpoints. For the Internet embodiment, information is transmitted in Internet protocol (IP) packets using transport control protocol/Internet protocol (TCP/IP). It will be understood that information may be transmitted in other suitable packets, including asynchronous transport mode (ATM) and other cells or datagrams.

The servers 52 may comprise voicemail servers (VMS), fax/modem servers, short message center (SMSC) servers, conferencing facilities, authentication, authorization, and accounting (AAA) servers, billing servers, home location registers (HLR), home subscriber servers (HSS), domain name servers (DNS), location servers and other suitable servers and functionality providing services to mobile devices 36 and/or to wireless and/or wireline connections in the communications system 10.

The servers 52 and/or other elements of the wireless or wireline networks 12 and 14 store subscriber level information for users of the wireless and/or wireline networks 12 and 14. The service level information includes service, quality and/or service level agreement (SLA) parameters for user connections. In a particular embodiment, the BSCs 32 store or access SLA databases including a QoS policy for each user. The QoS identifies a class of service (CoS) for user connections. The CoS identifies drops, delays, jitter, relative priority and other limits for the user connections. It will be understood that subscription level information may be otherwise stored and/or accessed for each bandwidth request for call set up, additional bandwidth or call handoff in the communications network 10.

FIG. 2 illustrates a bandwidth allocation controller 70 for the wireless network 12 in accordance with one embodiment of the present invention. In this embodiment, the bandwidth allocation controller 70 as well as other components of the communications system 10 comprises logic encoded in media for implementing bandwidth request control and other suitable functionality of the system. The logic comprises functional instructions for carrying out program task upon execution. The media comprises computer disks or other computer-readable media, application specific integrated circuits (ASIC), field programmable gate arrays (FPGA), digital signal processors (DSP), other suitable specific or general purpose processors, transmission media or other suitable media in which logic may be encoded and utilized.

Referring to FIG. 2, the bandwidth allocation controller 70 controls bandwidth request for connections in a cell 34 of the wireless network 12 to prevent the cell 34 from exceeding its maximum transmit power and thereby damaging its transmitter. The bandwidth allocation controller 70 includes a call bandwidth control 72 and a handoff admission control 74. The call bandwidth control 72 receives and processes call admission and additional bandwidth request for existing calls within the cell 34. The handoff admission control 74 receives and processes handoff requests for existing connections entering the cell 34. The request includes subscription level information, which may be the subscription level or information from which the subscription level of a connection associated with the request can be determined, and user and/or mobile identification.

The bandwidth controller 70 may be implemented in the BTS 30, BSC 32, MSC 40 or other suitable component of or coupled to the wireless network 12. The bandwidth controller may also be distributed in the wireless network 12. For example, the call bandwidth control 72 may reside at MSC 40 while the handoff admission control 74 resides at the BSCs 32. In addition, it will be understood that the bandwidth allocation controller 70 may implement a single bandwidth control including the functionality and elements of the call bandwidth control 72 and the handoff admission control 74. In this embodiment, blocking thresholds and queues may be shared for each type and/or category of bandwidth request or may be separated out for one or more types and/or categories of bandwidth requests. For example, higher priority request necessary to prevent dropping of an ongoing call may share a single higher blocking threshold while lower priority request for new calls desired to be made or additional bandwidth for ongoing calls may have a lower blocking threshold.

The call bandwidth control 72 includes a call bandwidth blocking threshold 80, call admission queues 82 and additional bandwidth queues 84. The call bandwidth blocking threshold 80 identifies a transmit power level of the cell over which a new call or additional bandwidth for an ongoing call or other suitable connection will be blocked. A connection may be a voice call, a video call, a data call, a combination of a voice video and/or data call or may comprise any other suitable information. In a particular embodiment, the call bandwidth blocking threshold may be eighty (80) percent of the maximum transmit power level of the cell 34.

The call admission queues 82 include a plurality of distinct queues each corresponding to a specific CoS, QoS or other subscription level priority parameter for a connection. The queues may be physically, logically or otherwise distinct such that request in each queue may be identified and processed based on a priority of the queues. Within each queue, the request may be processed in a FIFO or other suitable order.

In the illustrated embodiment, call admission queues 82 include a premium queue 86, an assured queue 88, and a best effort queue 90. Each queue is operable to queue a plurality of request 92. It will be understood that the call admission queues 82 may comprise other or different subscription-level based queues into which request 92 for admission of a call may be segregated and processed based on priority.

The additional bandwidth queues 84 also include a plurality of distinct queues each corresponding to a specific CoS, QoS or other subscription level priority parameter for connection. The queues may be physically, logically or otherwise distinct such that requests in each queue may be identified in process based on a priority of the queues. Within each queue, the request may be processed on a FIFO or other suitable order.

In the illustrated embodiment, the additional bandwidth queues 84 include a premium queue 94, an assured queue 96 and a best effort queue 98 each operable to queue one or more additional bandwidth requests 100. It will be understood that the additional bandwidth queues 84 may comprise other or different subscription-level based queues into which request 100 for additional bandwidth of a connection may be segregated and processed based on priority.

In operation, call admission and additional bandwidth requests 92 and 100 are received by the call bandwidth control 72 and forwarded to a corresponding one of the queues based on the type of the request and the subscription level for the connection to which the request corresponds. Requests in the premium queues 86 and 94 are processed first with requests in the assured queues 88 and 96 processed next followed by requests in the best effort queues 90 and 98. In a particular embodiment, call admission request of a priority are processed prior to the additional bandwidth request of the same priority. Thus, for example request 100 in the premium additional bandwidth queue 94 are processed after request 92 in the premium call admission queue 86 and request 100 in the best effort additional bandwidth queue 98 are processed only if all other requests in all other queues have been processed. After each request in a queue is processed, the call bandwidth control 72 may determine whether any new request 92 and/or 100 have been received in higher priority queues before processing the next highest priority queue or the next request in the currently processed queue. In this way, priority-based processing is maximized by the call bandwidth control 72.

The handoff admission control 74 includes a handoff blocking threshold 110 and handoff queues 112. The handoff blocking threshold 110 identifies the power level of the cell 34 over which handoff requests will be blocked. In one embodiment, the handoff blocking threshold 110 is independent of subscription level and thus the same for all handoff requests received by the cell 34. Typically, the handoff blocking threshold 110 is higher than that or those for call admission and additional bandwidth requests to provide priority to ongoing connections entering the cell 34. In a particular embodiment, the handoff blocking threshold 110 may be ninety (90) percent of the maximum transmit power of the cell 34.

The handoff queues 112 include a plurality of distinct queues each corresponding to a specific CoS, QoS or other subscription level priority parameter for a connection. The queues may be physically, logically or otherwise distinct such that requests in each queue may be identified and processed based on a priority of the queues. Within each queue, the request may be processed in a FIFO or other suitable order.

In the illustrated embodiment, handoff queues 112 include a premium handoff queue 114, an assured handoff queue 116 and a best effort queue 118 each operable to queue one or more handoff requests 120. It will be understood that handoff queues 112 may comprise other or different subscription level-based queues into which requests 120 for the handoff of connection may be segregated and processed based on priority.

In operation, handoff requests 120 are received by the handoff admission control 74 and forwarded to a corresponding one of the handoff queues 112 based on the subscription level for the connection to which the request corresponds. Requests in the premium queue 114 are processed first with requests in the assured queue 116 processed next followed by request in the best effort queue 118. Thus, for example, requests 120 in the best effort queue 118 are only processed if all other requests 120 in all other handoff queues 112 have already been processed. After each request 120 in a queue is processed, the handoff admission control 74 may determine whether any new requests 120 have been received in higher priority queues before proceeding to the next highest priority queue or a next request in the currently processed queue. In this way, priority-based processing is maximized by the handoff admission control 74.

The priority-based queues allow power, or bandwidth, of the cell to be maximized up to a single threshold level while still providing subscription-based priority to requests. In another embodiment, subscription-based blocking thresholds may be used to allow requests to be processed in the order received using a single queue but based on priority of the associated connection. It will be understood that one or the other of the priority-based call blocking thresholds or priority-based queues may be used by both the call admission control and handoff admission control 72 and 74. In yet another embodiment, a single control may be used for call admission, handoff and additional bandwidth requests with the requests being queued and allocated bandwidth blocking based on priority of the request and/or request type. In one or more and/or other embodiments, the priority-based processing of requests ties the bandwidth request servicing mechanisms to the network quality mechanisms such that users with higher subscription levels will observe higher allocated bandwidths compared to users with lower subscription levels. The QoS, CoS, or other network quality mechanism may be provided to the bandwidth allocation controller 70 during radio bandwidth reservation at the start of a call and or the start of the bandwidth request. Thus, the wireless service provider can deliver differentiated tiered services to mobile users based on their subscription level.

FIG. 3 illustrates a method for queuing bandwidth request for allocation in a wireless network in accordance with one embodiment of the present invention. In this embodiment, a single bandwidth request control including the functionality, thresholds and queues of the call bandwidth control 72 and handoff admission control 74 is utilized.

Referring to FIG. 3, the method begins at state 160 in which the bandwidth request control is idle while there are no requests to be processed. In response to a bandwidth request for a connection, idle state 160 transitions to step. At step 162, the type of the request is determined. The request may be a handoff request, a call admission request, an additional bandwidth request or any other suitable type of request for bandwidth for a wireless connection. Proceeding to step 162, a QoS policy is retrieved for the connection. The QoS policy may be retrieved from a SLA or other suitable database or node of the communications network 10.

Next, at step 164, a CoS is determined for the connection based on the QoS policy. The CoS may be specified in the QoS policy or otherwise determined based on subscription or rate information in the QoS policy. At step 166, the request is queued into a corresponding one of the priority-based queues. Thus, for example, if the request is for handoff of a premium connection, the request is queued in the premium handoff queue 114 while if the request is for additional bandwidth of a best effort connection, the request is queued in the best effort queue 98.

Step 166 returns to idle state 160. In idle state 160, the bandwidth request control, in response to a request reaching a delay threshold, transitions to step 168. At step 168, the request is cleared. Step 168 transitions back to idle state 160. Thus, bandwidth requests are cleared as they reach a delay threshold. In another embodiment, expired request may be cleared periodically.

FIG. 4 illustrates a method for bandwidth allocation control in accordance with one embodiment of the present invention. In this embodiment, as previously described in connection with FIG. 3, a single bandwidth request control is used to process call handoff, call admission and additional bandwidth requests. The bandwidth request control includes the call bandwidth and call handoff admission controls 72 and 74 and/or the functionality, thresholds and queues of the controls 72 and 74.

Referring to FIG. 4, the method begins at step 200 in which bandwidth usage for the cell in which requests are being processed is updated to reflect the current, real-time bandwidth usage of the cell. The bandwidth usage may be updated by the BTSs 30 and passed to the bandwidth allocation controller 70 or determined and/or estimated by the controller.

Proceeding to the decisional step 210, the bandwidth request control determines whether the premium handoff queue 114, or other highest priority queue, contains any requests. If the premium handoff queue 114 includes one or more requests, the Yes branch of decisional step 210 leads to decisional step 212. At decisional step 212, it is determined whether the next request is permitted based on the SLA for the connection. If the connection is not subscribed to use bandwidth resources in the cell, the request is not permitted and the No branch of decisional step 212 leads to step 218. If the request is permitted, the Yes branch of decisional step 212 leads to step 214.

At decisional step 214, it is determined whether the handoff blocking threshold 110 would be exceeded if the next request is allowed. In one embodiment, the threshold is exceeded if current bandwidth usage plus the requested bandwidth exceeds the threshold. If the handoff blocking threshold 110 would not be exceeded by the request, the No branch of decisional step 214 leads to step 216 in which the next request is allowed. Step 216 leads to step 218 in which the request is cleared from the queue. Step 218 returns to step 200 in which the bandwidth usage for the cell is updated and processing of request in the queues begins again starting with the highest priority queues.

Returning to decisional step 212, if the next, request is not permitted regardless of bandwidth usage, the No branch of decisional step 212 leads to step 218 where the request is cleared from the queue without further processing. Returning to decisional step 214, if the request will exceed the handoff blocking threshold 110, the Yes branch of decisional step 214 returns to step 200 without allowing the request. Thus, the request is only allowed or allowed to the extent that the corresponding threshold is not exceeded.

After all requests in the premium handoff queue 114 are processed, the No branch of decisional step 210 leads to decisional step 220. At decisional step 220, the bandwidth request control determines whether the premium call admission queue 86 contains any requests. If the premium call admission queue 86 contains one or more requests, the Yes branch of decisional step 220 leads to decisional step 222.

At decisional step 222, the bandwidth request control determines whether allowing the next request would cause the cell to exceed the call bandwidth blocking threshold 80. If the threshold is not exceeded, the No branch of decisional step 222 leads to step 224 in which the request is allowed. Next, at step 226, the allowed request is cleared. Step 226 returns to step 200 in which the bandwidth usage is again updated and processing of requests in the queues begins again starting with the highest priority queues.

Returning to decisional step 222, if the request would exceed the call bandwidth blocking threshold 80, the Yes branch of decisional step 222 returns to step 200 without allowing the next request. Thus, the request will only be allowed if doing so does not cause the corresponding blocking threshold to be exceeded.

After all requests in the premium call admission and higher priority queues are processed and/or cleared, the No branch of decisional step 220 leads to decisional step 230. At decisional step 230, the bandwidth request control determines whether the premium additional bandwidth queue 94 contains any requests. If the premium additional bandwidth queue 94 includes one or more requests, the Yes branch of decisional step 230 leads to decisional step 232.

At decisional step 232, the bandwidth request control determines whether allowing the next request in the queue 94 would cause the call bandwidth blocking threshold 80 to be exceeded. If the blocking threshold 80 would not be exceeded, the No branch of decisional step 232 proceeds to step 234 in which the next request is allowed. Next, at step 236, the request is cleared from the queue 94. Step 236 returns to step 200 in which the bandwidth usage is again updated to reflect the bandwidth allocated to the processed request plus any other bandwidth use changes in the cell.

Returning to step 232, if the next request would exceed the call bandwidth blocking threshold 80, the request is not allowed in the Yes branch of decisional step 232 returns to step 200 without allowance of the request. Accordingly, the next request will remain queued until sufficient bandwidth is available or until a delayed threshold is reached in which case it will be cleared.

After all requests in the premium queues are processed and/or cleared, the No branch of decisional step 230 leads to the decisional step 240 in which the bandwidth request control determines whether the assured handoff queue 116, or other highest priority queue, contains any requests. If the assured handoff queue 116 includes one or more requests, the Yes branch of decisional step 240 leads to decisional step 242. At decisional step 242, it is determined whether the next request is permitted based on the SLA for the connection. If the connection is not subscribed to use bandwidth resources in the cell, the request is not permitted and the No branch of decisional step 242 leads to step 248. If the request is permitted, the Yes branch of decisional step 242 leads to step 244.

At decisional step 244, it is determined whether the handoff blocking threshold 110 would be exceeded if the next request is allowed. In one embodiment, the threshold is exceeded if current bandwidth usage plus the requested bandwidth exceeds the threshold. If the handoff blocking threshold 110 would not be exceeded by the request, the No branch of decisional step 244 leads to step 246 in which the next request is allowed. Step 246 leads to step 248 in which the request is cleared from the queue. Step 248 returns to step 200 in which the bandwidth usage for the cell is updated.

Returning to decisional step 242, if the next request is not permitted regardless of bandwidth usage, the No branch of decisional step 242 leads to step 248 where the request is cleared from the queue without further processing. Returning to decisional step 244, if the request will exceed the handoff threshold 110, the Yes branch of decisional step 244 returns to step 200 without allowing the request. Thus, the request is only allowed or allowed to the extent that the corresponding threshold is not exceeded.

After all requests in the assured handoff and higher priority queues are processed and/or cleared, the No branch of decisional step 240 leads to decisional step 250. At decisional step 250, the bandwidth request control determines whether the assured call admission queue 88 contains any requests. If the assured call admission queue 88 contains one or more requests, the Yes branch of decisional step 250 leads to decisional step 252.

At decisional step 252, the bandwidth request control determines whether allowing the next request would cause the cell to exceed the call bandwidth blocking threshold 80. If the threshold is not exceeded, the No branch of decisional step 252 leads to step 254 in which the request is allowed. Next, at step 256, the allowed request is cleared. Step 256 returns to step 200 in which the bandwidth usage is again updated and processing of requests in the queues begins again starting with the highest priority queues.

Returning to decisional step 252, if the request would exceed the call bandwidth blocking threshold 80, the Yes branch of decisional step 252 returns to step 200 without allowing the next request. Thus, the request will only be allowed if doing so does not cause the corresponding blocking threshold to be exceeded.

After all requests in the assured call admission and higher priority queues are processed and/or cleared, the No branch of decisional step 250 leads to decisional step 260. At decisional step 260, the bandwidth request control determines whether the assured additional bandwidth queue 96 contains any requests. If the assured additional bandwidth queue 96 includes one or more requests, the Yes branch of decisional step 260 leads to decisional step 262.

At decisional step 262, the bandwidth request control determines whether allowing the next request in the queue 96 would cause the call bandwidth blocking threshold 80 to be exceeded. If the blocking threshold 80 would not be exceeded, the No branch of decisional step 262 proceeds to step 264 in which the next request is allowed. Next, at step 266, the request is cleared from the queue 96. Step 266 returns to step 200 in which the bandwidth usage is again updated to reflect the bandwidth allocated to the processed request plus any other bandwidth use changes in the cell.

Returning to step 262, if the next request would exceed the call bandwidth blocking threshold 80, the request is not allowed in the Yes branch of decisional step 262 returns to step 200 without allowance of the request. Accordingly, the next request will remain queued until sufficient bandwidth is available or until a delayed threshold is reached in which case it will be cleared.

After all premium and assured requests are processed and/or queued, the No branch of decisional step 260 leads to the decisional step 270 in which the bandwidth request control determines whether the best effort handoff queue 118 contains any requests. If the best effort handoff queue 114 includes one or more requests, the Yes branch of decisional step 270 leads to decisional step 212. At decisional step 272, it is determined whether the next request is permitted based on the SLA for the connection. If the connection is not subscribed to use bandwidth resources in the cell, the request is not permitted and the No branch of decisional step 272 leads to step 278. If the request is permitted, the Yes branch of decisional step 272 leads to step 274.

At decisional step 274, it is determined whether the handoff blocking threshold 110 would be exceeded if the next request is allowed. In one embodiment, the threshold is exceeded if current bandwidth usage plus the requested bandwidth exceeds the threshold. If the handoff blocking threshold 110 would not be exceeded by the request, the No branch of decisional step 274 leads to step 276 in which the next request is allowed. Step 276 leads to step 278 in which the request is cleared from the queue. Step 278 returns to step 200 in which the bandwidth usage for the cell is updated.

Returning to decisional step 272, if the next request is not permitted regardless of bandwidth usage, the No branch of decisional step 272 leads to step 278 where the request is cleared from the queue without further processing. Returning to decisional step 274, if the request will exceed the handoff blocking threshold 110, the Yes branch of decisional step 274 returns to step 200 without allowing the request. Thus, the request is only allowed or allowed to the extent that the corresponding threshold is not exceeded.

After all requests in the best effort handoff and higher priority queues are processed and/or cleared, the No branch of decisional step 270 leads to decisional step 280. At decisional step 280, the bandwidth request control determines whether the best effort call admission queue 90 contains any requests. If the best effort call admission queue 90 contains one or more requests, the Yes branch of decisional step 280 leads to decisional step 282.

At decisional step 282, the bandwidth request control determines whether best effort allowing the next request would cause the cell to exceed the call bandwidth blocking threshold 80. If the threshold is not exceeded, the No branch of decisional step 282 leads to step 284 in which the request is allowed. Next, at step 286, the allowed request is cleared. Step 286 returns to step 200 in which the bandwidth usage is again updated and processing of requests in the queues begins again starting with the highest priority queues.

Returning to decisional step 282, if the request would exceed the call bandwidth blocking threshold 80, the Yes branch of decisional step 282 returns to step 200 without allowing the next request. Thus, the request will only be allowed if doing so does not cause the corresponding blocking threshold to be exceeded.

After all requests in the higher priority queues are processed, the No branch of decisional step 280 leads to decisional step 290. At decisional step 290, the bandwidth request control determines whether the best effort additional bandwidth queue 98 contains any requests. If the best effort additional bandwidth queue 98 includes one or more requests, the Yes branch of decisional step 290 leads to decisional step 292.

At decisional step 292, the bandwidth request control determines whether allowing the next request in the queue 98 would cause the call bandwidth blocking threshold 80 to be exceeded. If the blocking threshold 80 would not be exceeded, the No branch of decisional step 292 proceeds to step 294 in which the next request is allowed. Next, at step 296, the request is cleared from the queue 98. Step 296 returns to step 200 in which the bandwidth usage is again updated to reflect the bandwidth allocated to the process request plus any other bandwidth use changes in the cell.

Returning to step 292, if the next request would exceed the call bandwidth blocking threshold 80, the request is not allowed in the Yes branch of decisional step 292 returns to step 200 without allowance of the request. Accordingly, the next request will remain queued until sufficient bandwidth is available or until a delayed threshold is reached in which case it will be cleared.

In this way, requests are processed based on priority. It will be understood that if sufficient bandwidth is not available for a request, the request may be granted at a reduced bandwidth such that the corresponding blocking threshold is not exceeded or that the queues may be searched for highest priority allowable request. It will be further understood that the queue processing order may be altered to support a suitable processing scheme.

Although the present invention has been described with several embodiment, various changes and modifications may be suggested to one skilled in the art. It is intended that the present invention encompass such changes and modifications as fall within the scope of the appended claims and their equivalents. 

1. (canceled)
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. (canceled)
 6. (canceled)
 7. (canceled)
 8. (canceled)
 9. (canceled)
 10. (canceled)
 11. (canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)
 15. (canceled)
 16. (canceled)
 17. (canceled)
 18. (canceled)
 19. (canceled)
 20. (canceled)
 21. (canceled)
 22. (canceled)
 23. (canceled)
 24. (canceled)
 25. (canceled)
 26. (canceled)
 27. (canceled)
 28. (canceled)
 29. (canceled)
 30. (canceled)
 31. (canceled)
 32. (canceled)
 33. (canceled)
 34. (canceled)
 35. (canceled)
 36. (canceled)
 37. (canceled)
 38. (canceled)
 39. (canceled)
 40. A method for managing real-time bandwidth requests in a wireless network, comprising: queuing each of a plurality of bandwidth requests in a corresponding one of a plurality of class of service (CoS) queues, the bandwidth requests requesting establishment of a connection to a cell of a wireless network; and processing, by queue, the plurality of bandwidth requests from the plurality of CoS queues in order of a CoS priority of the queues.
 41. The method of claim 40, further comprising establishing a connection based on subscription level information of each bandwidth request.
 42. The method of claim 41, wherein the subscription level information comprises a quality of service (QoS), and further comprising processing each bandwidth request in an order based on the QoS.
 43. The method of claim 42, wherein processing each of the bandwidth requests in an order based on the QoS comprises: retrieving a QoS policy for the connection; determining the CoS for the connection based on the QoS policy; queuing each bandwidth request in the corresponding CoS queue; and processing each bandwidth request after bandwidth requests in higher priority CoS queues have been processed.
 44. The method of claim 43, further comprising clearing each bandwidth request after a delay threshold for the bandwidth request is reached.
 45. The method of claim 40, wherein each bandwidth request comprises a call admission request, an additional bandwidth request, or a handoff request.
 46. The method of claim 40, wherein at least one of the bandwidth requests is a call origination request.
 47. The method of claim 40, wherein at least one of the bandwidth requests is a handoff request.
 48. The method of claim 40, wherein the connection is an existing connection, and at least one of the bandwidth requests is an additional bandwidth request for the connection.
 49. The method of claim 40, further comprising determining a priority associated with the connection based on subscription level information, wherein the subscription level information of each bandwidth request comprises a CoS.
 50. The method of claim 40, wherein processing the plurality of bandwidth requests comprises processing each bandwidth request corresponding to a highest priority CoS and in a descending order of CoS priority.
 51. The method of claim 40, further comprising clearing from the queues any bandwidth request reaching a delay threshold.
 52. The method of claim 40, wherein the CoS priority comprises a subscription level.
 53. The method of claim 40, further comprising processing each bandwidth request by determining whether allowing each bandwidth request would exceed a blocking threshold for the cell.
 54. The method of claim 53, wherein the cell comprises a plurality of blocking thresholds, and further comprising processing each bandwidth request by determining whether allowing each bandwidth request would exceed a corresponding blocking threshold.
 55. The method of claim 54, wherein the cell comprises a call bandwidth blocking threshold for call admission and additional bandwidth requests and a handoff blocking threshold for call handoff requests.
 56. A system for managing real-time bandwidth requests in a wireless network, comprising: means for queuing each of a plurality of bandwidth requests in a corresponding one of a plurality of class of service (CoS) queues, the bandwidth requests requesting establishment of a connection to a cell of a wireless network; and means for processing, by queue, the plurality of bandwidth requests from the plurality of CoS queues in order of a CoS priority of the queues.
 57. The system of claim 56, further comprising means for establishing a connection based on subscription level information of each bandwidth request.
 58. The system of claim 57, wherein the subscription level information comprises a quality of service (QoS), and further comprising means for processing each bandwidth request in an order based on the QoS.
 59. The system of claim 58, wherein processing each of the bandwidth requests in an order based on the QoS comprises: means for retrieving a QoS policy for the connection; means for determining the CoS for the connection based on the QoS policy; means for queuing each bandwidth request in the corresponding CoS queue; and means for processing each bandwidth request after bandwidth requests in higher priority CoS queues have been processed.
 60. The system of claim 59, further comprising means for clearing each bandwidth request after a delay threshold for the bandwidth request is reached.
 61. The system of claim 56, wherein each bandwidth request comprises a call admission request, an additional bandwidth request, or a handoff request.
 62. The system of claim 56, wherein at least one of the bandwidth requests is a call origination request.
 63. The system of claim 56, wherein at least one of the bandwidth requests is a handoff request.
 64. The system of claim 56, wherein the connection is an existing connection, and at least one of the bandwidth requests is an additional bandwidth request for the connection.
 65. The system of claim 56, further comprising means for determining a priority associated with the connection based on subscription level information, wherein the subscription level information of each bandwidth request comprises a CoS.
 66. The system of claim 56, wherein processing the plurality of bandwidth requests comprises processing each bandwidth request corresponding to a highest priority CoS and in a descending order of CoS priority.
 67. The system of claim 56, further comprising means for clearing from the queues any bandwidth request reaching a delay threshold.
 68. The system of claim 56, wherein the CoS priority comprises a subscription level.
 69. The system of claim 56, further comprising means for processing each bandwidth request by determining whether allowing each bandwidth request would exceed a blocking threshold for the cell.
 70. The system of claim 69, wherein the cell comprises a plurality of blocking thresholds, and further comprising means for processing each bandwidth request by determining whether allowing each bandwidth request would exceed a corresponding blocking threshold.
 71. The system of claim 70, wherein the cell comprises a call bandwidth blocking threshold for call admission and additional bandwidth requests and a handoff blocking threshold for call handoff requests.
 72. Logic embodied in a computer readable medium, the computer readable medium comprising logic operable to: queue each of a plurality of bandwidth requests in a corresponding one of a plurality of class of service (CoS) queues, the bandwidth requests requesting establishment of a connection to a cell of a wireless network; and process, by queue, the plurality of bandwidth requests from the plurality of CoS queues in order of a CoS priority of the queues.
 73. The computer readable medium of claim 72, the logic operable to establish a connection based on subscription level information of each bandwidth request.
 74. The computer readable medium of claim 73, wherein the subscription level information comprises a quality of service (QoS), and the logic operable to process each bandwidth request in an order based on the QoS.
 75. The computer readable medium of claim 74, wherein processing each of the bandwidth requests in an order based on the QoS comprises logic operable to: retrieve a QoS policy for the connection; determine the CoS for the connection based on the QoS policy; queue each bandwidth request in the corresponding CoS queue; and process each bandwidth request after bandwidth requests in higher priority CoS queues have been processed.
 76. The computer readable medium of claim 75, the logic further operable to clear each bandwidth request after a delay threshold for the bandwidth request is reached.
 77. The computer readable medium of claim 72, wherein each bandwidth request comprises a call admission request, an additional bandwidth request, or a handoff request.
 78. The computer readable medium of claim 72, wherein at least one of the bandwidth requests is a call origination request.
 79. The computer readable medium of claim 72, wherein at least one of the bandwidth requests is a handoff request.
 80. The computer readable medium of claim 72, wherein the connection is an existing connection, and at least one of the bandwidth requests is an additional bandwidth request for the connection.
 81. The computer readable medium of claim 72, the logic further operable to determine a priority associated with the connection based on subscription level information, wherein the subscription level information of each bandwidth request comprises a CoS.
 82. The computer readable medium of claim 72, wherein processing the plurality of bandwidth requests comprises processing each bandwidth request corresponding to a highest priority CoS and in a descending order of CoS priority.
 83. The computer readable medium of claim 72, the logic further operable to clear from the queues any bandwidth request reaching a delay threshold.
 84. The computer readable medium of claim 72, wherein the CoS priority comprises a subscription level.
 85. The computer readable medium of claim 72, the logic further operable to process each bandwidth request by determining whether allowing each bandwidth request would exceed a blocking threshold for the cell.
 86. The computer readable medium of claim 85, wherein the cell comprises a plurality of blocking thresholds, and the logic further operable to process each bandwidth request by determining whether allowing each bandwidth request would exceed a corresponding blocking threshold.
 87. The computer readable medium of claim 86, wherein the cell comprises a call bandwidth blocking threshold for call admission and additional bandwidth requests and a handoff blocking threshold for call handoff requests. 